J1-P31-Fx BASE

1. Informations

Document release	Hardware release	Description	Note	Date

Document:	MIMJ1P31F BASE
Description:	Installation and maintenance manual
Editor:	Riccardo Furlato
Approver	Gabriele Bazzi
Link:	https://www.qem.eu/doku/doku.php/strumenti/qmoveplus/j1P31/mimj1P31fx_base
Language:	English

01	02	New manual	Valid from software release 1P31F-xx.5.3	05/12/2012
02	02	Adding the 1MG5F card	/	06/03/2013
03	02	New “BASE” varsion of this manual	/	12/02/2015
04	02	Added the section “General information”	/	03/11/2015

CE Marking and reference standards

The controller has been designed for industral environments in conformity to EC directive 2004/108/CE.

EN 61000-6-4: Electromagnetic compatibility - Generic standard on emission for industrial environments
- EN55011 Class A: Limits and measurement methods

EN 61000-6-2: Electromagnetic compatibility - Generic standard on immunity for industrial environments
- EN 61000-4-2: Electromagnetic compatibility - Electrostatic discharge immunity
- EN 61000-4-3: Immunity to radiated, radio-frequency electromagnetic field
- EN 61000-4-4: Electrical fast transients
- EN 61000-4-5: Surge immunity
- EN 61000-4-6: Conducted disturbance induced by radio-frequency

Moreover the product is conform to the following standards:
- EN 60529: Housing protection rating IP64
- EN 60068-2-1: Environmental testing: Cold
- EN 60068-2-2: Environmental testing: Dry heat
- EN 60068-2-14: Environmental testing: Change of temperature
- EN 60068-2-30: Environmental testing: Cyclic damp heat
- EN 60068-2-6: Environmental testing: Sinusoidal vibration
- EN 60068-2-27: Environmental testing: Shock vibration
- EN 60068-2-64: Environmental testing: Random vibration

2. Description

The J1-P31-F is a combo HMI-PAC controller of the Qmove+ range.

2.1 Product Identification

	The Ordering Code provides the exact product features. Make sure that the product characteristics meet your requirements.

2.1.1 Product Label

a - Ordering Code
b - Week made: indicates the week and year of manufacture
c - Part number: unique code that identifies an ordering code
d - Serial number: product serial number, different for individual product
e - Hardware release: version of hardware release

2.1.2 Ordering Code

Model				Features
J1	-	P31	-	FA	-	10	/	TP01
								TP00 = Keypad code (TP00 = panel with resistive, logo and custom function keys); TP01 = panel with resistive touch-screen, logo and QEM standard function keys
						10 = Firmware version (00 = not installed)
				F = Technology level A = Hardware version
		P = Basic keypad (only function keys) 3 = 7” LCD graphic display, TFT-256 COLORS-800x480px; front panel dimensions (216x168mm); keypad 7 keys + 11 led; housing to DIN 43700; 1 = Firmware-hardware correspondence
J1 = “HMI+PLC” Qmove family

2.1.3 Hardware Versions

These are hardware versions currently available:

		Hardware versions
		A	B	C	D	E	F	G	H	I	J	K	L	M	Y	W	Z
SLOT 2 (Base card)	USER PORT	1	1	1	1	1	1	1	1	1	1	1	1	1	1	1	1
	AUX1 PORT (RS232, RS422, RS485)	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	1
	AUX2 PORT (RS485)	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	1
	CAN1 PORT	1	1	1	1	1	1	1	1	1	1	1	1	1	1	1	1
	CAN2 PORT¹⁾	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	ETHERNET PORT	-	-	-	-	1	1	-	1	-	-	1	1	1	1	1	1
	USB PORT²⁾	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
SLOT 3 (Specialization cards)	Standard digital inputs	-	16	16	16	16	16	16	16	16	16	16	16	16	16	-	16
	Rapid digital inputs³⁾	-	2	2	2	2	2	2	2	2	2	2	2	2	2	-	2
	Analog inputs 12bit	-	2	2	2	2	2	2	2	2	2	2	4	2	2	-	2
	Analog inputs 16bit	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	PT100 inputs⁴⁾	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Termocouple inputs⁵⁾	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Bidirectional counters 20KHz ABZ (24V-PP, 5V-LD)	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Bidirectional counters 200KHz ABZ (24V-PP, 5V-LD)	-	2	4	2	2	4	4	2	2	4	4	2	-	4	-	4
	SSI absolute counters	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Protected digital outputs	-	8	8	8	8	8	8	16	16	16	16	16	16	8	-	8
	Relay digital outputs	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Analog outputs 0-10V-12bit	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
	Analog outputs +/-10V-16bit	-	2	4	2	2	4	4	2	2	4	4	2	-	4	-	4
	Stepper outputs	-	-	-	2	-	-	4	-	2	-	-	-	-	4	-	4
	Remote keyboards connector⁶⁾	-	-	-	-	-	-	-	-	-	-	-	-	-	1	-	1
Card software code declared in SLOT 3		-

^{1),
2),
4),
5),
6)} option not currently enabled

³⁾ 2 rapid inputs can be used as frequency meters inside the “FREQ” device

2.1.4 Expansion card manuals

1MG3F rel.02

1MG5F rel.01

2.1.5 Firmware versions

Version	Description
10	Fully programmable with PLC functions
20	Fully programmable with PLC and Motion control functions
30	Fully programmable with PLC, Motion control, Camming and Interpolation functions

For more details about the firmware, consult Devices enabled in the controllers.

2.2 Product Configuration

2.2.1 Front panel

A) Function keys and led's
B) System led's

2.2.2 Back terminal blocks

The J1-P31-F s composed of a “base” card and an “expansion” card.

a = Expansion card
b = Base card power supply connector
c = Base card

3. Technical features

3.1 General features

Weight (full hardware)	1Kg
Housing	Sheet metal
Front panel	Alluminium
Outer Frame	Self-extinguishing Noryl
Display	LCD 7'' TFT 256 colors - 800 x 480px
Touch screen	wire Resistive
Display dimensions	152,4 x 91,4mm / 7“
User led's	14
System led's	8
Function keys	7
System keys	3
Operating temperature	0 ÷ 50°C
Transport and storage temperature	-25 ÷ +70 °C
Relative humidity	90% condensate free
Altitude	0 - 2000m s.l.m.
Front protection rating	IP64

3.2 CPU (F level technology)

RISC microprocessor (32 bit)
Work frequency	200MHz
RAM	16MB
Flash	8MB

3.3 Dimensions

	Lengths in mm

3.4 Hole template

3.5 Installation

Fit the controller in the hole.

Apply the brackets.

	Before fixing the controller, check it is mounted firmly in the hole and the gasket under the frame makes a good seal. No liquids must enter and the frame must not deform.

Screw the controller in place.

	Warning: after putting the pin of fixing, do only half rotation to not tear the frame!

4. Base card wiring

	For details about cable sections and connectors, see application note AN021

4.1 Power Supply

	The cabling must be carried out by specialist personnel and fitted with suitable anti-static precautions. Before handling the controller, disconnect the power and all parts connected to it. To guarantee compliance with EC regulations, the power supply must have a galvanic isolation of at least 1500Vac.

Power supply	24 Vdc
Voltage range	22 - 27 Vdc
Max. absorption	30W

Connector

Terminal	Symbol	Description
1	+	DC power positive
2	GROUND	Gnd-PE (signals)
3	-	DC power 0V

Connection examples

	Use an isolated power unit with 24Vdc +/-5% output conform to EN60950-1.

	Use two separate power units: one for the control circuit and one for the power circuit
	For a single power unit, use two separate lines: one for the control and one for the power
	DO NOT use the same lines for the power circuit and the controller

4.2 Serial Port Connections

4.2.1 PROG PORT

PROG PORT	Description
	Serial port used for the transfer and debugging of the application program in the CPU. Use only with IQ009 or IQ013.

4.2.2 USER PORT

Connector

Terminal	RS232	RS422	RS485	Description
1A	-	-	A	Terminal A - RS485
2A	-	-	B	Terminal B - RS485
3A	0V	0V	0V	USER PORT common
4A	0V	0V	0V USER PORT common
5A	TX	-	-	Terminal TX - RS232
6A	Terra
1B	-	RX	-	Terminal RX - RS422
2B	-	RXN	-	Terminal RX N - RS422
3B	-	TX	-	Terminal TX - RS422
4B	-	TXN	-	Terminal TX N - RS422
5B	RX	-	-	Terminal RX - RS232
6B	Ground

Setup of USER PORT electric standard

Num. Dip	Name DIP	Setting of DIP			Function
1	JP2	ON	X¹⁾	X²⁾	Termination RS485
2	JP3	ON	X³⁾	X⁴⁾	Polarization RS485
3	JP1	ON	X⁵⁾	X⁶⁾	Polarization RS485
4		OFF	ON	OFF	Selection of USER PORT electric standard
5		ON	OFF	OFF
6		OFF	OFF	ON
		RS485	RS422	RS232⁷⁾

^{1),
2),
3),
4),
5),
6)} X = setting not significant

⁷⁾ the USER PORT can be used as PROG PORT with RS232 electric standard, setting ON in DIP-8 of SW1 and OFF in DIP-6 of SW2

4.2.3 AUX1 PORT

Connector

Terminal	RS232	RS422	RS485	Description
1A	-	-	A	Terminal A - RS485
2A	-	-	B	Terminal B - RS485
3A	0V	0V	0V	USER PORT common
4A	0V	0V	0V	USER PORT common
5A	TX	-	-	Terminal TX - RS232
6A	Ground
1B	-	RX	-	Terminal RX - RS422
2B	-	RXN	-	Terminal RX N - RS422
3B	-	TX	-	Terminal TX - RS422
4B	-	TXN	-	Terminal TX N - RS422
5B	RX	-	-	Terminal RX - RS232
6B	Ground

Setup of AUX1 PORT electric standard

Num. Dip	Name DIP	Setting of DIP			Function
1	JP2	ON	X¹⁾	X²⁾	Termination RS485
2	JP3	ON	X³⁾	X⁴⁾	Polarization RS485
3	JP1	ON	X⁵⁾	X⁶⁾	Polarization RS485
4	-	OFF	ON	OFF	Standard USER PORT settings
5	-	ON	OFF	OFF
6	-	OFF	OFF	ON
-	-	RS485	RS422	RS232

^{1),
2),
3),
4),
5),
6)} X = setting not significant

4.2.4 AUX2 PORT

Connector

Terminal	Symbol	Description
1	0V	RS485 serial common
2	B	Terminal RS485 B
3	A	Terminal RS485 A

Setup of AUX2 PORT polarisation and termination resistances

Num. Dip	Name Dip	Setting of DIP	Function
1	JP3	ON	Polarization RS485
2	JP2	ON	Termination RS485
3	JP1	ON	Polarization RS485
4		X¹⁾	None

¹⁾ X = setting not significant

4.2.5 CANbus PORT

Connectors

Terminal	Symbol	Description
1	0V	CAN common
2	CAN L	Terminal CAN L
3	CAN H	Terminal CAN H

Setup of CAN1 and CAN2 PORT Termination resistances

Num. Dip	Name Dip	Setting of DIP	Function
1	JP1	ON	CAN1 Termination
2	JP2	ON	CAN1 Termination
3	JP1	ON	CAN2 Termination
4	JP2	ON	CAN2 Termination

	When activating the CAN1 port termination, set dip's JP1 and JP2 to ON. When activating the CAN1 port termination, set dip's JP1 and JP2 to ON.

4.2.6 Ethernet

ETHERNET PORT	Description
	Connector RJ45. LED: * LINK: green led = cable connected (led on signals the cable is connected to both ends) * DATA: yellow led = data transmission (flashing led signals data transmission)

4.2.6.1 MMC/SD

Memory card slot (marked by an arrow)

5. Electrical features

The electrical characteristics of the hardware are given below.
The maximum and minimum frequencies, and real acquisition times, may depend on eventual additional software filters “QMOVE:sys004” section variables of system.

5.1 PROG PORT

Connector for IQ009 or IQ013

	The USB mini-B connector does not support USB electrical standards, it can only be used with an interface IQ009 or IQ013.

It is used for the transfer and debugging of the application program in the CPU.

Electrical standard	TTL (Use serial interface IQ009 or IQ013)
Communication speed	Min. 9.6 Kbaud - max 115200 Kbaud settable by dip1 and 2 of the switch SW1
Insulation	None


Connection between Qmove+ e PC using the accessory IQ009


Connection between Qmove+ and a device fitted with a RS232 serial port (e.g. a MODEM), using the interface IQ013

5.2 RS232

Communication speed	4800, 9600, 19200, 38400, 57600, 115200 baud
Communication mode	Full duplex
Operating mode	Referred to 0V
Max. number of devices connected on the line	1
Max. cable length	15 m
Input impedence	> 3 Kohm
Short-circuit current limit	7 mA

5.3 RS422

Communication speed	4800, 9600, 19200, 38400, 57600, 115200 baud
Communication mode	Full duplex
Operating mode	Differential
Max. number of devices connected on the line	1
Max. cable length	1200 m
Input impedence	> 12 Kohm
Short-circuit current limit	35 mA

5.4 RS485

	To activate the internal termination resistance see paragraph Setup of USER PORT electric standard, Setup of AUX1 PORT electric standard or Setup of AUX2 PORT polarization and termination resistances

Communication speed	4800 baud (only if used with SERCOM and/or MODBUS device), 9600 baud, 19200 baud, 38400 baud, 57600 baud
Communication mode	Half duplex
Operating mode	Differential
Max. number of devices connected on the line	32
Max. cable length	1200 m
Input impedence	> 12 Kohm
Short-circuit current limit	35 mA

5.5 CANbus

To activate the internal termination resistance see paragraph Setup Termination resistances

Communication speed	125, 250, 500, 1000 Kbit/s
Max. number of Drivers/Receivers on the line	100
Max. cable lengths	500m @ 125Kbit/s, 250m @ 250Kbit/s, 100m @ 500Kbit/s, 25m @ 1000Kbit/s
Input impedence	>15Kohm
Short-circuit current limit	45mA

CAN BUS connection examples.

Caution:
Close DIP's JP1 and JP2 and insert the termination resistances (RL, RH) on the last device of the chain.

5.6 Ethernet

Ethernet Interface 10/100 Base T (IEEE 802.3) on RJ45 connector.

Connection between Qmove + and PC:


Qmove+	Cross-over cable EIA/TIA-568A/B	PC

5.7 MMC/SD

Type of Memory Card to use

MMC, SD and SDHC up to 8GB
For proper operation it is necessary that the device conforms to the standards set by “SD Association” (www.sdcard.org) or “Multi Media Card Association” (www.mmca.org).

	To use the Memory Cards they must first be formatted with FAT16 or FAT32 file system.

6. Settings, procedures and signals

6.1 PROG PORT and USER PORT Baud-rate selector

Dip	DIP settings				Function
1	OFF	OFF	ON	ON	Select PROG PORT transmission speed
2	OFF	ON	OFF	ON
	Baud-rate 38400	Baud-rate 115200	Baud-rate 19200	Baud-rate 57600

3	OFF	OFF	ON	ON	Select USER PORT transmission speed
4	OFF	ON	OFF	ON
	Baud-rate 38400	Baud-rate 115200	Baud-rate 19200	Baud-rate 57600

5	CANbus baud-rate selector. See paragraph CANbus baud-rate selector

6	OFF		ON		Select PROG PORT functioning mode
	PROG PORT can also be used by SERCOM and MODBUS devices		PROG PORT cannot be used by SERCOM and MODBUS devices		Select PROG PORT functioning mode

7	CANbus baud-rate selector. See paragraph CANbus baud-rate selector

8	OFF		ON		Select the USER PORT as PROG PORT¹⁾
	PROG PORT normal		PROG PORT on USER PORT connector		Select the USER PORT as PROG PORT¹⁾

¹⁾ It is possible to use the USER PORT connector as PROG PORT with RS232 electric standard, doing this the mini-USB connector of the PROG PORT is disconnected (Setting USER PORT electric standard). For this function mode also set dip 6 of SW2 to OFF.

6.2 Baud-rate CANbus selector

Dip	DIP settings				Function
1	-				-
2	-				-
3	-				-
4	-				-

5	OFF	ON	OFF	ON	Select speed of CANbus transmission
7	OFF	OFF	ON	ON
	Baud-rate 125KB/S	Baud-rate 250KB/S	Baud-rate 500KB/S	Baud-rate 1MB/S

6	-				-
8	-				-

6.3 Led

The system leds “pow, run, stop, err” are found on the front panel and on the rear of controllers with display and only on the top of controllers without display.

The user leds “L1, L2, L3 e L4” are found on the rear:

“System Leds” Signals

Leggend:

Led ON

Led OFF

Led Blinking

Led	Colour	Description
pow	Green	Power on
pow	Green	Only this led on, signals the CPU reset status
run	Green	CPU in RUN status
run	Green	CPU in READY status
stop	Yellow	With pow on, signals the STOP status of the CPU With pow off, signals the BOOT status of the CPU
err	Red	With pow off, signals a hardware error. See paragraph Hardware Error codes With pow blinking, the flash rate gives the type of error. See paragraph err led signals

Err led signals

N. flashes	Error	Description	Recommended action
1	Bus error	Bus configuration different to application software.	Check the correspondence between the QMOVE application (BUS section of configuration unit) and the product configurations (cards mounted in BUS).
2	CheckSum Error	Negative outcome on the integrity control of retentive variables . (see Reset Error Checksum)	Restore the machine data from a backup (.DAT file) or cancel the error with in system functions and enter the values manually.
3	Index Out of Bound	An array index is pointing on an inexistent element	Open a unit editor in Qview development environment and use the “Edit→Go to PC” command to find the program line that is cause of the error. In general the index value has a value <1 or >array dimension.
4	Program Over Range	The program selection index in the DATAGROUP has attempted to access an inexistent program.	With the Qview development environment open the editor of a unit and user the “Edit→Go to PC” command to highlight the program line that has caused the error. In general the value used as index is lower than 1 or over the array dimension.
5	Step Over Range	The step selection index in the DATAGROUP has attempted to access an inexistent step.	With the Qview development environment open the editor of a unit and user the “Edit→Go to PC” command to highlight the program line that has caused the error. In general the value used as index is lower than 1 or over the array dimension.
6	Division By Zero	The denominator of a division operation of the application program has a zero value.	With the Qview development environment open the editor of a unit and user the “Edit→Go to PC” command to highlight the program line that has caused the error.
7	Syntax Error	The application program has an invalid instruction	This error may appear because the program counter has met the QCL END instruction.
8	Watch Dog Error	A CAN module does not function correctly, or a specialist card has a hardware problem	With the Qview development environment open the “Monitor→Bus” panel and the righthand column called “Watchdog Bus” indicates the card that caused the problem.
9	Stack Error	The applciation program has used all permitted levels of calls to subroutines	With the Qview software environment open the editor of a unit and use the “Edit→Go to PC” command to highlight the program line that caused the error. Analyse the unit execution flow, the call to subroutines nestings have a limit, over which this error is generated.

Hardware error codes

During the startup sequence, if a malfunction of any peripheral is detected, the system blocks and the error is signaled by the flashing led err while the other system led's remain off.

The number of flashes indicates the type of error according to the following table :

Number of flashes	Error
1	Display
2	FPGA
3	Media
4	Bootloader
5	FW
6	Bus
7	Signal not active
8	Signal not active
9	Exception

	Each of these signals indicates a serious error situation. The product must be sent to the QEM aftersales service.

“User Led” signal

Led	Colour	Description
L1	Yellow	Programmable in the application program by the QMOVE system variable:sys003 and used by the system functions
L2
L3
L4

6.4 Keys

Name	Description
FUNC	Press on startup of the controller to access the System functions
BOOT	Press on startup of the controller to set the CPU in Boot status and then access the firmware update functions
RESET	Reset CPU. the system is restarted restoring the initial conditions (after a startup )

7. General information of operation

7.1 Introduction

This chapter will introduce some concepts and describes some operations of the product. These contents are partly related and implemented in firmware. This software implements all features that allow the product to be a component of the system programmable Qmove.

7.2 Organizing data and memories

To best understand the terms used in this chapter, it is important to know the organisation of data and memory in a QMOVE application. QMOVE applications are programs written in QCL language that, translated in binary code, are transferred onto QMOVE hardware and saved there. In the hardware, the microprocessor runs has a program called firmware that interprets the above binary code instructions and performs the operations associated to them.

A QCL application, in addition to the instructions, is also composed of variables that the QCL instructions act on.. Some of these variables are retentive, i.e. their values remain unaltered from shut-off to start up. The flow chart below illustrates the organisation of data in a QCL application transferred to the memory of any QMOVE hardware:

It can be noted that, the QMOVE hardware has several mass storage devices:

“Flash memory”, where the following is saved:

QCL program: the series of QCL instructions translated into binary by the compiler.
HMI program: the series of HMI screens translated into binary by the compiler. This program only exists when the QMOVE hardware has a display.
Configuration data: the calibration and configuration data, the touch-screen calibration settings, the ethernet communication configuration data (IP address, etc…), etc.

“Non volatile memory”, which stores:

Retentive variables: the group of variables that remains unaltered on a shut-off and startup (e.g. SYSTEM, ARRAYS, DATAGROUP, etc).

“Volatile memory”, which stores:

Not retentive variables: the group of variables that is set to 0 at each startup (e.g. GLOBAL, ARRGBL, etc).

The volatile data memory is also used as dynamic memory. i.e. the memory used by the firmware for internal operations and active HMI screen management.

“Mass storage internal device” is managed by a standard filesystem and is useful to save information by the DATASTORE device (read - write binary or csv files with recipes, logs, variuous setups, etc).
It 'also used to store the backup of the application QMOVE and other service files.

“Mass storage external device” is managed by a standard filesystem and is useful for loading the QMOVE application, data loading/saving, firmware update or to save informations by the DATASTORE device.

7.3 CPU status

The CPU has several operating statuses. The figure below shows the main status changes from the controller startup.
The main operating statuses are RESET, READY, RUN and STOP.
The CPU events that determine a transition from one status to another are mainly linked to commands being sent by the development environment: Run, Reset, Stop and Restart.
Application download is the development environment procedure that allows to transfer a QMOVE application to the CPU.

Stati della CPU

BOOT state

The BOOT state can be used to access the firmware updating functions.

SELF-DIAGNOSIS state

During the startup, after scanning the system led's, the controller performs a series of self-diagnostic operations. When any faults are detected or the operator has to be informed of any given situation, the self-doagnosis procedure is temporarily interrupted, signalling the event.
The fault signal is made by led's L1, L2 and a message is given on display (if present).

System Messages

n.	Led ON	System Message (if display present)	Description	Type
1	L1	`System Data WRITE ERROR`	Indicates that a write error has occurred during the configuration data saving.	B
2	L2	`System Data IS RESTORED FROM DEFAULT`	Indicates that the configuration data has been restores to the default settings.	C
3	L1 L2	`System Data is updated` Please verify new data	Indicates that the configuration data has been converted into a new format. Check that the previous settings have been maintained.	C
4	L3	`Firmware is updated old: 1K31F10 1.001 new: 1K31F10 1.002`	Indicates that a firmware update has been made.	C

When the condition detected allows to continue to the start stage (type C) and waits for the FUNC button or for the F1 key to be pressed to continue the boot procedure.

If not provided with a display, the controller waits 5 seconds before continuing with the startup stage, without waiting for a button to be pressed.

When the situation does not allow to continue the startup stage (tipo B), the controller, if provided with a display, shows the message“PLEASE TURN OFF AND TURN ON THE SYSTEM” and remains in this state until you turn off. If the controller is not provided with a display, the led err flashes continuously.

SYSTEM BOOTING state

During the SYSTEM BOOTING state instruments with displays, displays some important information about the system as in the example shown in the following figure:

	WARNING: The values shown in the figure are examples and may vary according to the instrument.

List of the information displayed

n.	Message	Description
1	`Boot status: POWER-ON`	It displays the status of the boot: POWER-ON Switching on the instrument INIT Download application initialization RESTART Restarting the instrument software BACKUP Performing the Backup RESTORE Performing the Restore
2	`Firmware: 1K31F-30.5.6`	They show the name, version, major releases and minor releases of firmware. In the example we have: 1K31F Firmware name 30 Version 5 Major release 6 Minor release (build)
3	`S/N: 12345678`	This displays the serial number of the instrument.
4	`Date(DMY)/Time: 31/12/2010 - 12:34:56`	The clock/calendar is displayed in the format: DD/MM/YYYY - hh:mm:ss
5	`Dip-Switch = 0x2E`	It displays a hexadecimal value representing the status of the switch SW1. It is equivalent to the value of the system variable SYS002.
6	`MMC: PRESENT 510/31250 KB`	If a MMC/SD is inserted into the slot, at this stage we are displayed device data such as KB used (510) and KB total (31250). In the case where the device is not present is displayed “not present !”
7	`NAND: PRESENT 40510/63794 KB`	It checks for all of the internal NAND, and then displays the KB used and KB total. In the case where the device is not detected, an error is reported and is displayed “NAND: NOT PRESENT !”
8	`Touch Screen: PRESENT`	Instruments equipped with a touch screen, it is detected and then are verified the calibration data. In the event that has yet to be performed calibration, the message diplayed is “CALIBRATION REQUIRED !”. The touchscreen calibration is possible with the system function “Touch Calibration”.
9	`ETHERNET: IP = 192.168.0.253 NM = 255.255.255.0 GW = 0.0.0.0`	On instruments equipped with Ethernet interface, displays the parameters IP address (IP), subnet mask (NM) and Gateway (GW). Changing these values is possible with the system function “Set Ethernet communic. parameter” or through special programs available within the development environment.
10	`BACKUP: VALID QCL App: 25/04/2001 - 16:58:07 MATCH QCL Dat: 25/04/2001 - 16:58:37 MATCH QTP App: 25/04/2001 - 17:01:15 MATCH`	It is checked for a valid backup in NAND and then displays the data of date and time of backup files relating to the application QCL (QCL App), the application data QCL (QCL Dat) and to the application QTP (QTP App). If after “BACKUP” is displayed “VALID” means that the backup can be successfully restored by system function “Restore from NAND”. If after “BACKUP” appears “NOT PRESENT” it means that the backup is not present. If after “BACKUP” is displayed “NOT VALID” means that the backup can not be restored properly as the checksum of the three files that make up are not consistent with each other. After each file (QCL App, QCL Dat and QTP App), in addition to the information of the date and time of creation, is also displayed further information: “MATCH” indicates that the file is consistent with the running application. “NO MATCH” indicates that the file is not consistent with the running application. “SIZE ERROR” indicates that the size of the file is invalid, possibly because the writing procedure was not completed correctly. “NOT PRESENT” indicates that the file is not present.
11	`Press F1/FUNC for 2s to System Functions`	The display of this message indicates that the pressure for at least 2 seconds of the F1 key or the FUNC button provides access to system functions as described in the procedure. The message is displayed for 4 seconds.
12	`!!! WARNING detected !!! Press FUNC or F1 to continue`	If during the previous phases, they are displayed some warning messages, which do not affect the operation of the system, to allow the operator to easily read the screen is waited a time of about 20 seconds. To not wait and go before, press the F1 key or the FUNC button.
13	`!!! ERROR detected !!! Press FUNC or F1 to continue`	Message displayed if the previous phases are displayed some error messages. To continue, press the F1 key or the FUNC button.

SYSTEM FUNCTIONS status

The SYSTEM FUNCTIONS status can be used to access the SYSTEM FUNCTIONS, which are special procedures that allow the user to perform various operations. For more details see the System Functions chapter.

RESET status

Led status	pow run
Status cause	No application in memory.
The condition that can put the CPU in this status	RESET command.

This condition can only pass onto a READY status by downloading the applicaiton, using the Qview6 development environment.

READY status

Led status	pow run
Status cause	Application valid and waiting for execution.
Conditions that can put the CPU in this status	Application download.

This condition can pass onto to the RUN or RESET statuses.

RUN status

Led status	pow run
Status cause	Application in execution.
Condition that can put the CPU in this status	RUN command.

This condition can pass onto all other CPU statuses.

STOP status

Led status	pow stop » run
Status cause	Stop on application in execution.
Condition that can put the CPU in this status	A breakpoint has been encountered in the application code interpretation.

This condition can pass onto all other CPU statuses.

7.4 System functions

	IMPORTANT: The use of these procedures could represent a risk (e.g. deletion of application), therefore it is highly recommended that they are performed by qualified experts.

The system functions are speficic procedures that allow the user to perform various operations, e.g. the configuration/calibration of peripherals, data and application save/restore on/from removable mass memory, deletion of the application and management of the mass memories.
Controllers with display have some system functions that are only accessible by password and if access attempts are made the “Function is locked” message is given.

All the system functions are listed below.
If the “PWD” column shows 'Y', this means that the function requires a system password (default: “123”).
DEVICE indicates an external storage media. MMC / SD or USB for hardware that they have the port.

System Functions

n.	Led ON	System Functions	PWD	Description
1	L1	01 - Reset Error Checksum	-	Reset checksum error. NOTE: if the checksum error is present, the led L1 flashes.
2	L2	02 - Copy all files DEVICE → NAND	-	Copy all files from DEVICE to NAND Flash memory.
3	L1 L2	03 - Copy all files NAND → DEVICE	-	Copy all files from NAND Flash memory to DEVICE.
4	L3	04 - Application delete	Y	Delete the application.
5	L1 L3	05 - Application upload from DEVICE	Y	Upload the application from DEVICE.
6	L2 L3	06 - System Settings	-	Adjust the system clock and selection of the DEVICE (only for hardware that possess both ports).
7	L1 L2 L3	07 - Downl. retentive data to DEVICE	-	Save the retentive data on DEVICE.
8	L4	08 - Set NEW Password	Y	Set a new password to access the “locked” system functions.
9	L1 L4	09 - Remove all files from NAND Flash	Y	Cancel all files stored on the NAND Flash memory.
10	L2 L4	10 - Show NAND Flash files	-	List the files stored on the NAND Flash memory.
11	L1 L2 L4	11 - Touch Calibration	-	Run the calibration procedure of the Touch Screen, if present.
12	L3 L4	12 - Set Ethernet communic. parameter	-	Run the setup procedure for the Ethernet communication parameters (IP address,…, etc.).
13	L1 L3 L4	13 - Backup to NAND	-	Run the backup of the QCL application, data and HMI application on NAND memory.
14	L2 L3 L4	14 - Restore from NAND	Y	Run the restore of the QCL application, data and HMI application from NAND memory.
15	L1 L2 L3 L4	15 - Firmware Upgrade	Y	Run the firmware upgrade from DEVICE. Available only in some hardware.

Note: To exit system functions press the keep the F1 key or FUNC button for at least two seconds.

Access to system functions

	To access the System Functions, start up the controller with FUNC button or F1 key pressed.

The QMOVE application, if present, it not executed and the led L1 lights up.
Tools that have a display appears “SYSTEM FUNCTIONS”.

	Use FUNC button or F1 key to scroll through the functions. The selected function is indicated by the combination of L1-L2-L3-L4 leds lighted up and in instruments that have a display, you see the selected function in the “SYSTEM FUNCTIONS”.

The “System Functions” table gives the list of system functions and related led combinations.

	Press BOOT button or F2 key for 2 seconds to execute the selected function. The POW led starts flashing to indicate that the selected function is being executed.

Instruments that have a display, you see the page “SYSTEM FUNCTIONS” as in the figure below.

When the function ends the POW led stops flashing.
Instruments that have a display, you see the page “SYSTEM FUNCTIONS” as in the figure below.

	Press FUNC button or F1 key to restart the controller.

If the function does not complete properly the POW stops and the ERR starts flashing.

The number of flashes indicates the type of error as shown in the table System Function Error Messages.

Error Messages

When a system function ends with an error, the number of led flashes err indicates the type of error.
If there is a display, a message is given to describe the cause of the error.

System Function Error Messages

Error/Number of ERR led flashes	Message
1	`Generic error`
2	`Open/Exist/Create file error`
3	`Read file error`
4	`Write file error`
5	`Out of Memory error`
6	`QMos Version error`
7	`Checksum Error`
8	`Symbols checksum No Match`
9	`Configuration / Symbols error`
10	`File format error`
11	`Format error`
12	`Device not present or unformatted`
13	`Application not present error`
14	`Touch calibration failure`
15	`File compression type not support`
16	`Target don't match project !`
17	`Fw version don't match project !`
18	`File copy error`
19	`File size error`
20	`Crypt operation error`
21	`Invalid Product Serial Number`
22	`Function is locked`
23	`Function not enabled`

Description of the functions

Reset Error Checksum

The system runs an integrity control of retentive variables by the applicaiton of a CRC to the nonvolatile data memory. This detects any corruption and prevents the application from starting up, signalling the situation by flashing the led err as shown in Err led signals.
For the application to function again, a new download of the application must be performed with the development environment, or the “Reset Error Checksum” system function. These operations delete the error status and zero-setsall retentive variables.

The procedure:

Check the error status and end the funciton if no error is present.
In microQMove products, the presence of the QCL application is also checked.
Vengono azzerati i dati ritentivi e viene visualizzato il messaggio “Clear power down data…” fino al termine della procedura.
Resets the retentive data and the message “Clear power down data…” until the end of the procedure.
End of operation

Copy all files DEVICE -> NAND

This procedure copies all files in the root and “DS” directory of the external MMC/SD or USB card to the NAND internal mass storage.

The following table gives the sequence of operations and any possible errors:

Message	Description	Possible errors
`Check DEVICE presence`	Checking for the presence of the external mass storage card On DEVICE appears MMC or USB, depending on what is selected	`Device not present or unformatted`
`Mounting device…`	Mounting the external mass storage card	`Device not present or unformatted`
`Searching files…`	Searching for compatible files	`No Files Found`
`Copy <filename>….`	Making a copy of the files indicating the name currently in copy

Copy all NAND files -> DEVICE

This procedure copies all files contained in the root and “DS” directory of the NAND internal mass storage to the external MMC/SD or USB card memory.

The following table gives the sequence of operations and any possible errors:

Message	Description	Possible errors
`Check DEVICE presence`	Checking for the presence of the external mass storage card On DEVICE appears MMC or USB, depending on what is selected	`Device not present or unformatted`
`Mounting device…`	Mounting external mass storage device	`Device not present or unformatted`
`Searching files…`	Searching for compatible files	`No Files Found`
`Copy <filename>….`	Copying the files indicating the name of the one currently in copy

Application delete

This deletes the application and empties the nonvolatible data memory, deleting the QCL program and, if present, deleting the HMI program.

The following table gives the sequence of operations performed and any possible errors:

Message	Description	Possible errors
`Reset retentive data`	Empty nonvolatible data memory	`Write file error`
`Delete QCL application`	Deletion of the QCL program	`Write file error`
`Delete HMI application`	Delection of the HMI program (if display installed)	`Write file error`

Application upload from DEVICE

This loads an application from the external MMC/SD or USB mass memory card to the non volatile memory.

This allows to load all or one of the QCL program, HMI program and retentive data.

The external MMC/SD or USB mass memory card must contain at least one of the following files:

applic.bin for the compiled QCL program generated by the Qview development environment
applic.dat for the data file generated by the “Save Data…” procedure of the Qview development environment or by the Downl system function. for retentive data to DEVICE;
appqtp.bin for the compiled HMI program generated by the Qpaint development environment; it is generated by the special function “Download the project to File…”.

Message	Description	Possible errors
`Check DEVICE presence`	Checking for the presence of the external mass storage card On DEVICE appears MMC or USB, depending on what is selected	`Device not present or unformatted`
`Mounting device…`	Mounting external mass storage card	`Device not present or unformatted`

If the applic.bin is present:

Message	Description	Possible errors
`Upload QCL application`	Uploading the QCL program	`Open/Exist/Create file error Write file error Read file error Out of Memory Error QMos Version Error Checksum Error Symbols checksum No Match Configuration / Symbols Error`

If the applic.bin file is not present, an application must already be loaded in the nonvolatile memory otherwise the “Application not present” message is given.

If the applic.dat file is present:

Message	Description	Possible errors
`Upload retentive data`	Uploading retentive data to the nonvolatile data memory	`Open/Exist/Create file error Write file error Read file error Out of Memory Error QMos Version Error Checksum Error Symbols checksum No Match Configuration / Symbols Error QTP File format error`

The procedure performs the following steps:

Check the presence of the MMC/SD or USB card.
The “Check DEVICE presence” message is given.
On DEVICE appears MMC or USB, depending on what is selected.
Mounting MMC/SD or USB card.\\The “Mounting device…” message is given.
Uploading the QCL program (applic.bin), if contained in the removable mass storage device
The “Upload QCL application” message is given.
Uploading retentive data of the QCL program (applic.dat), if contained in the removable mass storage device
The “Upload retentive data” message is given.
NOTE: if the applic.dat file is not found, the data in the system is maintained so long as the Symbol and Configuration checksums have not been varied. If they are varied all data will be set to zero.
Uploading the HMI program (appqtp.bin), if contained in the removable mass storage device
The “Upload HMI application” message is given.
The file is closed and the operation ends.

System Settings

This procedure sets the system clock/calendar and selects the type of external memory to be used.

The string Removable device is not present in hardware that does not have a USB port.
Press F2 key or BOOT button to enter a new setting in the boxes. Each time a setting is confirmed the next box is accessed for modification. At the last box the new settings are saved.

Downl. retentive data to DEVICE

This function creates a file on external mass storage (MMD/SD or USB) containing the retentive data values.
The file created is named “applic.dat” and is the same as the file obtained by the “Save Data…” procedure in the QView development environment. The function can only be performed if there is a valid QCL application in the controller.

The procedure performs the following steps:

Check the presence of the MMC/SD or USB card.
The “Check DEVICE presence” message is given.
On DEVICE appears MMC or USB, depending on what is selected.
Mounting the MMC/SD or USB card.
The “Mounting device…” message is given.
Check the presence of the QCL program
The “Checking application presence…” message is given.
Check the validity of the retentive data
The “Checking retentive data…” message is given.
Open the applic.dat destination file on the external MMC/SD or USB card
The “Open destination file…” message is given.
Write the headers in the destination file
The “Write headers to destination file” message is given.
Write the retentive data in the destination file
The “Write data to destination file”.
NOTE: the percentage progress of the operation is given during this step
Close the file and end the operation

Set NEW Password

This modifies the password to access the system functions. The password is a number. The default password is: 123 The procedure first asks for the current password (Actual Pwd) and, if correct, then allows a new password to be entered (New Pwd).

When the new password has been entered the “saving data…” message is given to indicate that the new data is being saved.

	If 0 (zero) is entered as a new password, the password request is disabled.

Remove all files from NAND Flash

Delete all files contained on the internal NAND flash mass storage.
Unlike the “Format NAND Flash” function, this acts at a filesystem level aqnd can therefore be performed as many times as necessary.

The procedure performs the following steps:

Calculation of the number of files contained in the internal mass storage.
The “Searching files…” message is given.
If zero files are found, the “No Files Found” message is given and the function ends, otherwise the “Delete <filename>” is given indicating the delection of every file found.
Close the internal storage and end procedure

Show NAND Flash files

This procedure views the name and size of all files found in the internal NAND flash mass storage.

The procedure performs the following steps:

Calculate the number of files in the internal mass storage.
The “Searching files…” message is given.
If zero files are found the “No Files Found” message is given and the procedure ends.
The file name and size in bytes “<filename> - <size>B” of each file found is shown.
Press the BOOT button or the F2 key again to continue with the next file when the “Press BOOT or F2 to show next filename” message is given.
Close the internal storage device and end procedure.

Touch Calibration

This procedure is used to calibrate the touch-screen device, if it's present.

At the entrance of the procedure, it is presented with a screen where there is a blue cross.
Press the center of the cross until the progress bar has reached completion.

At this point, the message “COMPLETED” and you can release the pressure.

Note: if the pressure is released before the completion of the progress bar, the procedure is aborted and the message “!! OPERATION ABORTED !!” is given.

Repeat for the other two crosses green and cyan.

Set Ethernet communic. parameter

This procedure views and modifies the communication parameters of the ETHERNET port.
When the function is accessed all data saved on the controller is shown.

To change a parameter press F2 and introduce the new setting.
Press ENTER to go to and change the next box.
When the last box is confirmed, the data is saved and the “saving data…” message is given.

If the Ethernet port is not present on the hardware, the message “Function not enabled” is given.

Backup to NAND

The backup procedure creates a copy of the QCL and HMI applications in execution and a dump of the retentive data, as files saved in the NAND mass storage. The files created have the following names:

applic.qcy identifies the file containing the QCL application (CPU)
appdat.qcy identifies the file containing the retentive data of the QCL application
appqtp.qcy identifies the file containing the HMI application

The procedure performs the following steps:

Check the presence of the QCL application
The “Checking application presence…” message is given.
Create and write in NAND the QCL application backup file: applic.qcy
The “Write QCL application” message is given with the percentage progress of the operation.
Check the presence and validity of retentive data of the QCL application
The “Checking retentive data…” message is given.
Create and write in NAND the retentive data backup file of the QCL application: appdat.qcy
The “Write QCL data” message is given with the percentage progress of the operation.
If the controller has a display, a check is made for the presence of the HMI application:
If the HMI application is correct the backup file appqtp.qcy is created in NAND and the “Write QTP application” message is given with the percentage progress of the operation.
If the application contains errors, the “QTP application error” message is given.
If the HMI application is not found, the “HMI application not present” message is given.
Procedure end and system reboot.

Restore from NAND

The restore procedure allows to recover from the NAND mass storage, the saved backup files of the QCL and HMI applications and an dump of the retentive data.

The procedure :

The message “Restore NAND backup” is given.
The NAND backup file of the QCL Application is read: applic.qcy
The message “Upload QCL application” is given, the percentage progress of the operation and the procedure step number.
The NAND backup file of the QCL Application retentive data is read : appdat.qcy
The message “Upload retentive data” is given, the percentage progress of the operation.
If the controller has a display, the presence of the HMI application is checked and read from the NAND back up file: appqtp.qcy.
The message “Upload HMI application” is given, the percentage progress of the operation and the procedure step number
Procedure end and system reboot.

Note to system functions Backup and Restore

The use of system functions Backup to NAND and Restore from NAND allows to save in backup and restore a QMOVE application.

The backup and restore operations use the NAND internal memory device. The backup procedure creates a file copy of the QCL program, the HMI program (if the controller has a Qem display) and an image of the ritentive data.

The files created:

applic.qcy containing the QCL program (QCL App)
appdat.qcy containing the ritentive data image (QCL Dat)
appqtp.qcy containing the HMI program (QTP App)

The files are encrypted and only the controller that generated them can run the Restore procedure so as to safeguard unauthorised data copies. The backup file copied to external memory such as MMC/SD or USB card can be carried out with the system function Copy all NAND files -> DEVICE. A directory named “QBK” is created in the MMC/SD or USB that contains the above files. In the same way backup files can be transferred to the controller using the system function Copy all files DEVICE -> NAND. In this case, the files in the MMC/SD or USB must always be contained in the directory “QBK”.

Backup/restore is an important function that can be used in the following cases:

to restore the QMOVE application to a known situation (the situation at the time of the backup), if data has been changed by an operator or if the machine data has been altered for any reason.
when testing a new application, a backup can be made of the original, stable version. If the new application being tested is not satisfactory, the restore command will recover the original version.

7.5 Information for programming

In this chapter are collected all the product information for programming.

Development suite

The product programming requires the Qview-6 environments to program the QCL code and if the product has a graphic display, also the QPaint-6 environment to design the screen graphics. Noth these softwares are available in the Qworkbench software package that can be downloaded as freeware from the Qem website (in “Support” section).

The contoller has 3 slots. The slots 4 to 32 can be declared and must be used to address recources installed in the Canopen modules.

To use the terminal in a product that has a display, you must declare under INTDEVICE the device MMIQ2.

INTDEVICE
   Hmi	MMIQ2	2

To program with the QPaint-6 development environment it is important to select the correct target. To do so, in the environment select Project → Target Configuration then select the right controller according to the ordering code.

Example of a statement of the BUS to use on the BUS unit's configuration:

BUS
   1	1P31F	10
   2	.	.
   3	1MG5F	.

The firmware versione must coincide, and if available, the specialization card name to the 3 slot must be correct. See the dedicate section.

Memorie utilizzate

In questo paragrafo vedremo come è possibile rilevare una stima dell'utilizzo delle memorie nel prodotto. La memoria non volatile, disponibile per memorizzare il programma QCL, ha una capacità di 512KB.
La quantità di memoria occupata è pari alla dimensione del file .BIN generato dal Qview. La percentuale di memoria occupata è visualizzabile nel pannello CPU del Qview, alla voce “Used CODE memory”, oppure è possibile ottenere questa informazione dal valore del parametro “sizeapp” del device QMOS.

La memoria non volatile, disponibile per memorizzare il programma HMI ha una capacità 5.5MB.
La quantità di memoria occupata è pari alla dimensione del file .BIN generato da Qpaint, il cui valore (in bytes) è visualizzato nel parametro “memqtp” del device MMIQ2.

La memoria dati non volatile, disponibile per memorizzare le variabili ritentive, ha una capacità di 819KB.
La percentuale di memoria occupata è visualizzabile nel pannello CPU del Qview, alla voce “Used RETENTIVE”, oppure è possibile ottenere questa informazione dal valore del parametro “sizeret” del device QMOS.

La memoria dati volatile per memorizzare le variabili non ritentive ha una capacità dipendente da vari fattori (per esempio la dimensione dei programmi HMI e QCL, della pagina HMI in visualizzazione ecc.)
La memoria generale del sistema libera, disponibile come memoria dati volatile, è indicata dal parametro “memfree” nel device MMIQ2.

Porte di comunicazione

Le seriali PROG PORT e USER PORT implementano il protocollo di comunicazione proprietario QEM chiamato BIN1.

I device SERCOM e MODBUS sono utilizzabili con tutte le seriali di comunicazione compresa la PROG PORT. Il valore numerico da utilizzare durante la dichiarazione del device per selezionare il canale di comunicazione è il seguente:

  0		PROG PORT
  1		USER PORT
  2		AUX1 PORT
  3		AUX2 PORT    (se disponibile nell'hardware)

Quando i devices SERCOM e MODBUS utilizzano la PROG PORT o la USER PORT essi interessano il canale solo se lo stato di comunicazione del device è aperto (st_opencom = 1). Quando il canale del device viene chiuso (st_opencom = 0) nella seriale ritorna attivo il protocollo BIN1. Se si volesse forzare il protocollo BIN1 sulla porta PROG (ed impedire quindi che il device SERCOM occupi il canale) è necessario attivare il dip 6 di SW1.

Quando si utilizza il protocollo MODBUS RTU sulla porta seriale USER, AUX1 e AUX2 con la configurazione elettrica RS485, bisogna fare attenzione al fatto che quando la seriale è in trasmissione lo strumento mantiene attivo il canale (DE) per un tempo superiore a quello stabilito dalla specifica “MODBUS RTU”. Per questo bisogna considerare un tempo minimo di 5 millisecondi dopo i quali sarà possibile ricevere un nuovo messaggio. Anche il device SERCOM quando termina una trasmissione è soggetto al medesimo tempo in cui viene mantenuto il canale attivo (DE).

La porta di comunicazione Ethernet utilizza il protocollo di trasporto TCP/IP dove i pacchetti del protocollo BIN1 vengono incapsulati all'interno dei pacchetti dati TCP/IP. Sono attive due connessioni identificate da due porte di comunicazione liberamente impostabili nei parametri di comunicazione della porta Ethernet. Se lo strumento dispone di display, questi valori sono visualizzati e modificabili attraverso la funzione di sistema 12 - Set Ethernet communic. parameter. Altre modalità per visualizzare e impostare questi dati sono realizzabili attraverso appositi programmi disponibili all'interno dell'ambiente di sviluppo (QConfigurator-1 e QConfigurator-2).

La porta impostata in “Port nr.1:” rappresenta un canale di comunicazione equivalente alla PROG PORT. La porta impostata in “Port nr.2:” rappresenta un canale equivalente alla USER PORT. Le porte 3 e 4 non sono attualmente utilizzate.

La porta Ethernet può essere inoltre usata per instaurare una comunicazione di tipo Modbus TCP-IP con altri dispositivi in rete. In questo caso il canale che identifica la porta ethernet è impostabile inserendo il numero 43.

mdbs   MODBUS   2   43

I 3 canali di comunicazione della porta ethernet (due con protocollo BIN e uno MODBUS TCP/IP) possono essere attivi contemporaneamente.

Messaggi di errore del firmware

Durante il download dell'applicativo Qmove l'ambiente di sviluppo QView-6 può visualizzare alcuni errori non descritti nel manuale dell'ambiente di sviluppo. Tali errori sono particolari e la stringa descrittiva visualizzata dal QView-6 viene generata direttamente dal firmware.

Nella seguente tabella sono descritti i possibili messaggi di errore generati dal firmware.

Messaggi d'errore firmware

Possibili messaggi d'errore	Descrizione
`Error: SYSTEM + ARRSYS + DATAGROUP + INTDEVICE size overflow by 234bytes.`	Compare quando le variabili ritentive superano il valore massimo consentito.
`Error: serial port not avaliable in SERCOM or MODBUS device declaration.`	Compare quando Il valore numerico utilizzato durante la dichiarazione del device per selezionare il canale di comunicazione è errato.
`Error: CANOPEN device required if you use more than 3 slots.`	Nella definizione del BUS si stanno utilizzando più di 3 slots e quindi l'applicazione richiede l'utilizzo di moduli Canopen. Per questa gestione è necessario dichiarare un device CANOPEN.
`Error: incorrect bus fault mode in CANOPEN declaration.`	Nella dichiarazione del device CANOPEN si è indicata una modalità di fault (ultimo valore nella dichiarazione) non supportata.
`Error: incorrect canbus speed in CANOPEN declaration.`	Nella dichiarazione del device CANOPEN si è indicata una velocità non valida.
`Error: too much CANOPEN device declaration.`	Può essere dichiarato un solo device CANOPEN.
`Error: absol. encoder resource num in ABSCNT device declar. is not avail.`	Nella dichiarazione del device ABSCNT si è indicata una risorsa che non esiste.
`Error: COUNT in ABSCNT device declaration is not a simulated counter.`	L'indirizzo del contatore utilizzato nella dichiarazione del device ABSCNT non è di tipo simulato (es: 1.CNT01).
`QMos version error. Unsupported instructions set.`	Una o più istruzioni nel progetto QCL non sono supportate dal firmware.
`Error: compression file type not support.`	La compressione del programma QCL compilato non è supportata dal firmware.
`Error: too mutch slots in bus declarations.`	Sono stati dichiarati nella sezione BUS più slot di quelli permessi dal tipo di hardware.

Variabili di sistema

L'ambiente di sviluppo mette a disposizione una serie di variabili predefinite che possono essere utilizzate precedendo al nome la parola chiave “QMOVE.”. Per esempio “QMOVE.is_suspend”, “QMOVE.sys001”, ecc. Lo scopo del presente paragrafo è illustrare le 16 variabili di sistema chiamate sys001÷sys016 il cui significato dipende dal firmware che si sta utilizzando.

sys001

Questa variabile a sola lettura indica lo stato dei pulsanti FUNC (bit 0) e BOOT (bit 1). I valori possibili sono dunque:
0 = nessun pulsante premuto.
1 = pulsante FUNC premuto.
2 = pulsante BOOT premuto.
3 = pulsanti FUNC e BOOT premuti.

sys002

Questa variabile permette la lettura dell'immagine del dip-switch SW1. L'immagine viene acquisita solo all'accensione del prodotto. Il bit 0 corrisponde al dip 1 e così via.

NB: Alcuni dip non sono collegati al microprocessore e quindi viene letto sempre al livello logico 0.

sys003

Questa variabile permette il comando del led L1-L2-L3-L4. Il bit 0 corrisponde a L1, il bit1 a L2 e così via.

sys004

Questa variabile permette l'impostazione del filtro anti-glitch ai segnali delle fasi nei contatori bidirezionali. Il valore è espresso in KHz e si riferisce alla frequenza del segnale di una fase. Il range di valori ammesso è 30÷220. Il valore impostato di default é 220KHz. La variabile può essere anche riletta. La modifica del filtro può essere fatta in qualsiasi momento.

sys005÷16

Non utilizzata.

7.5.1 I devices

Con il termine device si identifica una categoria di dispositivi software atti a svolgere attività di supporto e di controllo, più o meno complesse, per risolvere le problematiche legate all'automazione dei sistemi.
La lista dei devices implementati nel firmware dipende dalla versione firmware. Lo scopo del presente paragrafo è quello di illustrare la lista e le caratteristiche dei devices disponibili.

Il firmware versione 10 implementa i seguenti devices:

Nome device	Tempo di campionamento minimo (msec)	Tempo di campionamento massimo (msec)	Tempo di esecuzione (%)
ABSCNT	1	250	8,31
ANINP	1	250	14,25
CALENDAR	-	-	0
CANOPEN	1	250	100
COUNTER3	1	250	5,94
DAC	-	-	0
DATASTORE	1	20	90,5
FREQ	1	250	4,75
MMIQ2	1	10	90,5
MODBUS	1	250	32,07
QMOS	-	-	0
RECDATA	1	250	5,34
SERCOM	1	250	9,26

Il firmware versione 20 implementa anche i seguenti devices:

Nome device	Tempo di campionamento minimo (msec)	Tempo di campionamento massimo (msec)	Tempo di esecuzione (%)
ANPOS2	1	250	8,31
EANPOS	1	250	55,94
HEAD2	1	250	23,75
OOPOS3	1	250	27,91

Il firmware versione 30 implementa anche i seguenti devices:

Nome device	Tempo di campionamento minimo (msec)	Tempo di campionamento massimo (msec)	Tempo di esecuzione (%)
CAMMING3	1	250	55,94
INTERP	1	250	35,63
JOINT¹⁾	1	250	95,01

¹⁾ Il tempo di campionamento effettivo risulta essere doppio rispetta a quello impostato

Particolarità dei devices

In questo paragrafo vengono descritte delle informazioni aggiuntive sui devices. Queste informazioni integrano e completano il manuale di uso del device disponibile nel sito Qem. Sono informzioni relative all'implementazione del device in questo particolare prodotto.

CANOPEN

Se nella dichiarazione del device CANOPEN viene indicata la velocità zero allora essa diventa impostabile tramite dip di SW1.
Il primo slot per indirizzare risorse che risiedono all'interno di moduli Canopen è il 4.
Il firmware gestisce la cattura dell'ingresso in interruzione anche se questo è situato in un modulo Canopen.
E' possibile inserire il valore 2 nella dichiarazione del device sul campo relativo alla porta. Questa impostazione rende possibile lo startup dei drive DS402 tramite una richiesta QCL (QDO numero 10). Questa funzionalità si rende necessaria nei casi in cui ci siano dei drive senza ingresso di abilitazione e con l'alimentazione della parte logica in comune con l'alimentazione di potenza. Se la potenza è spenta il drive non comunica in CANOPEN poichè anche la parte logica è spenta.

DATASTORE

I files manipolati dal device DATASTORE sono tutti contenuti nella cartella /DS. Se questa cartella non esiste nel dispositivo essa viene creata automaticamente. Il device DATASTORE può operare sia con il dispositivo MMC/SD o USB che con una memoria tipo NAND interna al prodotto (non removibile). Per definire con quale dispositivo operare viene utilizzato il valore del parametro priority (0=MMC/SD, 1=NAND, 2=USB). Se l'applicazione deve frequentemente accedere ai due dispositivi supportati e non è richiesta la rimozione fisica del dispositivo MMC/SD o USB, è possibile utilizzare una particolare impostazione del parametro priority che evita di eseguire continuamente il MOUNT UMOUNT dei dispositivi. In pratica quando si desidera cambiare dispositivo prima di eseguire il comando UMOUNT si imposta “priority = -1”. Questo fa si che internamente al device la fase UMOUNT venga evitata rendendo il successivo comando MOUNT al medesimo dispositivo molto rapido.

Un esempio di codice QCL per cambiare dispositivo potrebbe essere:

SUB SETMMC
  WAIT NOT data.st_busy
  IF data.st_mount
    data.priority = -1
    data.UMOUNT
    WAIT NOT data.st_mount
    CALL CHECK_ERR_WRN
  ENDIF
  data.priority = 0
  data.MOUNT
  WAIT data.st_mount
ENDSUB
 
SUB SETNAND
  WAIT NOT data.st_busy
  IF data.st_mount
    data.priority = -1
    data.UMOUNT
    WAIT NOT data.st_mount
    CALL CHECK_ERR_WRN
  ENDIF
  data.priority = 1
  data.MOUNT
  WAIT data.st_mount
  CALL CHECK_ERR_WRN
ENDSUB

Esiste una particolare impostazione dei parametri che permette di verificare l'esistenza di un file nel dispositivo. Si utilizza il parametro “filenum” impostato al valore -1 e con il comando OPENFILE il device invece di aprire il file ricerca il primo file presente nella directory “/DS/” del dispositivo scelto. Quando trovato, il nome di tale file sarà impostato dal device nel parametro “filenum” stesso (ed il tipo nel parametro “filetype”). Impostando nuovamente -1 in “filenum” ed eseguendo il comando OPENFILE verrà cercato il nome del file successivo e così via. Ogniqualvolta verrà effettuata una operazione di OPENFILE con il filenum diverso da -1 il loop di ricerca verrà chiuso. Quando la ricerca sarà terminata e non vi saranno più file presenti, allora il device imposterà come risposta al comando OPENFILE “filenum = -2”. L'avvenuta esecuzione del comando sarà segnalata dal flag st_busy = 0. Se l'estensione del file non è HEX o CSV il file stesso viene ignorato dalla ricerca. Nel caso in cui il nome file non sia compatibile con quelli gestiti dal DATASTORE (numeri da 0 a 9999999) allora “filenum” rimarrà impostato a -1 e verrà segnalato un warning.

I parametri “disksize” e “diskfree” sono rappresentati in KB.

RECDATA

Il device può memorizzare un massimo di 10000 step.

QMOS

Il parametro “frwuvalue01” contiene il valore numerico del serial number del prodotto.

FREQ

Per definire l'ingresso associato al device FREQ utilizzare l'apposito campo numerico nella dichiarazione del device. La disponibilità di ingressi in frequenza deve essere verificata con la versione hardware del prodotto. Per ricavare la relazione tra valore numerico e pin del morsetto utilizzare le informazioni contenute nella colonna “Indirizzo” nelle tabelle di illustrazione del morsetto.

CAMMING3

I parametri relativi ai settori (CodeQm, CodeQs…) non sono ritentivi. All'accensione essi assumono sempre valore 0.